Release 10.1A: OpenEdge Development:
Progress Dynamics Repository Reference

rym_customization table — rymcz

This table captures the actual customization results for supported customization types, as defined in the ryc_customization_type table.

Table 2–7 lists the table’s FLA, fields, and foreign keys.

Table 2–7: rym_customization table information 

Table FLA	Fields (data type)	Foreign keys
rymcz	customization_type_obj (Decimal) customization_reference (Character) customization_result_obj (Decimal) customization_obj (Decimal)	customization_result_obj customization_type_obj

Table 2–8 gives details of the table’s indexes.

Table 2–8: rym_customization index information 

Index name	Elements	Type
XPKrym_customization	customization_type_obj customization_reference	Primary Unique
XIE1rym_customization	customization_reference	Nonunique
XIE2rym_customization	customization_obj	Nonunique
XIE3rym_customization	customization_result_obj	Nonunique

A mandatory join from the ryc_customization_type table defines each customization type. The customization_reference field is part of the unique key that stores customization values according to their types. For a user level customization, the customization_reference field contains a specific user’s login code. For a UI type customization, the field contains the value of a UI type, such as HTML or GUI.

There is a difference between the data in this table and the ryc_customization_result table. The ryc_customization_result table lists valid values for the result codes. This table stores actual values that can be checked at run time with the appropriate API. The values on this table might differ from the result code values on ryc_customization_result. The result code values are reusable.

For example, one customization type is user customization. On this table, there might be a record for each user with a reference pointing at each user’s login name. The API specified for the customization type runs to find the current user and looks up the specified result code for the user in this table. There might be several users whose result code value is “manager” and others whose result code value is “engineer.” Note the possible reuse of result codes and the difference between the result code values and the customization references.

This table stores the result of a customization through a join to the ryc_customization_result table, identifying the result code to use for this specific customization. These tables provide maximum flexibility for customization possibilities. The result codes for a session are evaluated after authentication and then made available to the session.

When reading from tables that support customization, such as ryc_smartobject and its related tables, if any matching customizations exist, the appropriate record is read with a matching result code of the highest priority level. Otherwise, the default record is used.